Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 5380 - Separate cleanAllRUV code into new file #5381

Merged
merged 1 commit into from
Jul 25, 2022

Conversation

mreynolds389
Copy link
Contributor

Description:

A majority of the cleanAllruv code is jammed inside of
rep5_replica_config.c. It really deserves it's own file which will make
it easier to analyze and troubleshoot (especially for people not
familiar with it).

Also, revised the CI "force" tests to make them more robust.

relates: #5380

Copy link
Contributor

@Firstyear Firstyear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This just moves the code? No other changes?

Copy link
Contributor

@jchapma jchapma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mreynolds389
Copy link
Contributor Author

This just moves the code? No other changes?

No changes to the server code, except I fixed a CI test to make it more robust

Description:

A majority of the cleanAllruv code is jammed inside of
rep5_replica_config.c. It really deserves it's own file which will make
it easier to analyze and troubleshoot (especially for people not
familiar with it).

Also, revised the CI "force" tests to make them more robust.

relates: 389ds#5380

Reviewed by: jchapman & firstyear (Thanks!!)
@mreynolds389 mreynolds389 merged commit 8f5db8d into 389ds:main Jul 25, 2022
@mreynolds389 mreynolds389 deleted the move-cleanallruv-code branch July 25, 2022 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants